
Nadya Lena
Twilight Federation
|
Posted - 2011.06.12 17:57:00 -
[1]
Edited by: Nadya Lena on 12/06/2011 18:04:03 I'm getting some errors with the sisilauncher update/repair...
(6/8) Downloading patch: 0.0%, 0 B /136.07 MB, 0 B /s, 00m00s (6/8) Downloading patch: 100.0%, 136.07 MB/136.07 MB, 1.44 MB/s, 36m15s
Both SiSiLauncher and the windows patch webinstaller have hilariously wrong speed calculations. I'm on an 1Mbit connection, my max speed is 110 KB/s.
(7/8) Applying patch: 0.0%, 0 B /1.39 GB, 0 B /s, 00m00s Restoring: resInteriorMinmatar.stuff Restoring: resInteriorPathGraphs.stuff Restoring: resInteriorRadiosityCache.stuff Traceback (most recent call last): File "repairTool\progressPanel.pyc", line 97, in _TaskRun File "repairTool\repairUI.pyc", line 78, in Start File "repairTool\repairLogic.pyc", line 147, in Repair File "repairTool\repairLogic.pyc", line 307, in Restore File "zsync\zsync.pyc", line 292, in RestoreFolder File "zsync\zsync.pyc", line 332, in ReconstructFiles KeyError: (-287691048, '*\x03\xec`\xd7\x13\xcbad\xb4| C!M\x15') Total Runtime: 0h39m28s
And this is the error I get.
This is actually the second run of the repair tool; the first run downloaded 1.02 GB of data and also failed in a similar way but I didn't worry, thinking it was a transient error.
EDIT: a third run finished successfully...
Improvement idea that probably was mentioned before: maybe you should use the rsync protocol or bittorrent for the repair tool...
|

Nadya Lena
Twilight Federation
|
Posted - 2011.06.12 23:10:00 -
[2]
Originally by: CCP Atropos
Originally by: Nadya Lena Improvement idea that probably was mentioned before: maybe you should use the rsync protocol or bittorrent for the repair tool...
Perhaps you should notice the name of the file that's listed as throwing the error, and do a google on it. You'll find that zsync IS rsync, but optimised for HTTP since we can't have a server doing custom diffs for everyone out there.
Indeed, my fail there D:
Originally by: CCP Atropos This error comes about when there's been some form of corruption when downloading data from the internet, so there's not really much that can be done.
Though the "rsync" idea came from seeing that the update is not done inplace and in a single batch (first downloading a blob that cannot be verified or repaired until zsync either works or fails), that there is no resume support or even timeout detection (unstable connections make installing large patches impossible).
|